apitech
/
Rocket.Chat
mirror of https://github.com/RocketChat/Rocket.Chat
1
0
Fork 0
Code Issues Projects Releases Wiki Activity
The communications platform that puts data protection first.
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
23800 Commits
718 Branches
1182 Tags
2.0 GiB
 
 
 
 
 
Tag: Branch: Tree: f7d2e27eec
Branches Tags
${ item.name }
Create tag ${ searchTerm }
Create branch ${ searchTerm }
from 'f7d2e27eec'
${ noResults }
Rocket.Chat/apps/meteor/client
History
Douglas Fabris f7d2e27eec
chore: `Table` in favor of `GenericTable` (#29628) 		3 years ago
..
UIKit/hooks
…
components feat: custom fields component to registration form (#29202) 3 years ago
contexts feat: Quick reactions on message toolbox (#29569) 3 years ago
definitions refactor(client): Remove dangling `direct` field on minimongo collections (#28833) 3 years ago
hooks feat: custom fields component to registration form (#29202) 3 years ago
lib regression(i18n): Broken translations on client-side startup (#29442) 3 years ago
methods refactor: create i18n package (#29097) 3 years ago
polyfills
…
portals
…
providers regression: `Contextualbar` size on wider screens (#29612) 3 years ago
sidebar fix: Show badge for threads direct mentions (#29587) 3 years ago
startup chore: load dialpad modal lazy (#29629) 3 years ago
stories
…
views chore: `Table` in favor of `GenericTable` (#29628) 3 years ago
.eslintrc.json chore: Add eslint `react-jsx-key` rule on client (#29581) 3 years ago
README.md
…
importPackages.ts chore: remove last templates using blaze (#29141) 3 years ago
main.ts chore: remove last templates using blaze (#29141) 3 years ago

README.md

How does the folder structure work in the frontend?

The folder structure should follow rocketchat's html 'semantics' like:

    main   -> room
                -> header
                    ...
                -> contextualbar
                    roominfo
                        ...
            -> sidebar
                -> Header
                    -> search
                    -> actions
                        ...
                -> list
                    ...
                -> footer
                    ...

Each folder is composed by:

File
index.jsx
ContainerComponent.jsx
contexts (optional)
providers (optional)
components (optional)
hooks (optional)
libs (optional)

We strongly suggest that you start developing your components/hooks/libs inside the folder where they will be directly used. If you ever find that you will use them in more than one place, then you should "promote" the code to an upper level, where it can be commonly accessed by all others

we have being moving code from blaze to react, but sometimes we will need render under blaze enviroment, to do that use createTemplateForComponent