docs: Add component guidelines for PlaceCal #2648
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Added component guidelines for PlaceCal. This will allow new contributors easily understand how to interact with components when developing.
Closed
15 tasks
kimadactyl
changed the title
|
confirmed working on staging 
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Added component guidelines for PlaceCal.
Checklist:
Resolves #2641
Work towards #2551 (the component guidelines item in the checklist)
Description
Added component guidelines for PlaceCal.
This will allow new contributors easily understand how to interact with components when developing.
Motivation and Context
This is meant to provide clarity on how we structure components in the PlaceCal repository as well as what we expect when new components are added/modified/removed
Relevant issues are #2641 as well as #2638 (the first PR in moving components from
mountain_viewtoview_component) for reading the discussions had there.Type of change
How Has This Been Tested?
By previewing the resulting markdown file.
Huly®: PC-2654