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.
 
 
 
 
 
Rocket.Chat/client
Douglas Fabris eb29b033fc
Regression: Add view room action on Teams Channels (#21295)
5 years ago
..
UIKit/hooks Regression: NPS (#20514) 5 years ago
components [NEW] Teams (#20966) 5 years ago
contexts [NEW] Teams (#20966) 5 years ago
hooks Regression: Add view room action on Teams Channels (#21295) 5 years ago
lib Improve: Increase testing coverage (#21015) 5 years ago
methods New eslint rules (#14332) 7 years ago
notifications [NEW] Channel avatar (#18443) 6 years ago
omnichannel [IMPROVE] Re-design Omnichannel Room Info Panel (#21199) 5 years ago
polyfills [NEW] Teams (#20966) 5 years ago
providers [NEW] Teams (#20966) 5 years ago
sidebar regression: Sidebar reactivity (#21296) 5 years ago
startup Fix non encripted rooms failing on send the message (#21287) 5 years ago
templateHelpers Message parsing and rendering - Phase 1 (#19654) 5 years ago
types [NEW] Teams (#20966) 5 years ago
views Regression: Add view room action on Teams Channels (#21295) 5 years ago
README.md Frontend folder structure (#19631) 5 years ago
adapters.js Rewrite Message action links (#20123) 5 years ago
head.html Depack: Use mainModule for root files (#13508) 7 years ago
importPackages.js [FIX] Custom emojis to override default (#20359) 5 years ago
main.js [NEW] Teams (#20966) 5 years ago
reactAdapters.js [NEW] Banner system and NPS (#20221) 5 years ago
routes.js [NEW] Omnichannel Contact Center (Directory) (#19931) 5 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: 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