Modifying Publishing Flux Components

[lcallif]

Accord to the doc: "At first, you might be hesitant to publish components because you won't receive automatic updates, howevever, this isn't as scary as it may first seem. To publish a component, run the following Artisan command....."

While it may not be scary, there is a concern that:

• Updates will not be able to be used as apps will be using the modified component in the published directory, retaining the same name.
• This will (or could) lead to misunderstandings of why the Component is not behaving as documented.
• New developers may have no idea that the components have been updated due to a wide number of reasons, thus allowing for the Component to be replaced / overridden. I know, these things should be documented but we all know this is not usually the case.

I believe it would be best if the documentation was to be changed to something like the following:

• Publish the Component(s) you will be making modifications to.
• Rename the directory(s) such that the original component is known.
• As an example, you want to modify the Button Component:
  • The project name is YourCodeIsAmazing
    • Publish the Button Component.
    • Prefix the directory with ycia_ with the resulting directory being called ycia_button

This allows for the use of the original button and/or the modified button. It also protects the modified Component from being accidentally overwritten.