Add replace prop to KRouterLink

[sairina]

Summary

Added replace prop to KRouterLink by making replace accessible within <router-link> component.

Addresses #85

[nucleogenesis]

Hey @sairina - we'll want to have the replace prop defined on the KRouterLink component as well - then the :replace="replace" in the template. I wasn't clear in the original issue, but the desire is to give the option to the implementer whether or not they want to replace.

I think that since the default is false on <router-link> we should make it the default in our KRouterLink as well

[sairina]

Thanks, for the clarification @nucleogenesis! Does this now work as intended?

Showing use of replace prop:

replace="true"

Expected behavior: the route to /test doesn't get added as a new history object; it replaces the current one (/info), so clicking the browser's back button takes it back to /content, and clicking the forward button takes it to /test, as /info has been replaced by /test.

** Flow: **

1. To - Channels (/content)
2. To - Info (/info)
3. To - Test (/test)
4. Back Arrow - Channels (/content)
5. Forward Arrow - Test (/test)

replace="false"

Expected behavior: the route to /test does get added as a new history object, so clicking the browser's back button takes it back to /info.

** Flow: **

1. To - Channels (/content)
2. To - Info (/info)
3. To - Test (/test)
4. Back Arrow - Info (/info)
5. Forward Arrow - Test (/test)

[nucleogenesis]

LGTM!

[indirectlylit]

To avoid ambiguity and undefined input values, component props should either be required: true or provide a default value.

In this case, the prop should be:

      replace: {
        type: Boolean,
        default: false,
      }

This ought to be caught by a linting rule. Can follow up separately on why it wasn't:
https://eslint.vuejs.org/rules/require-default-prop.html

[sairina]

Thank you! I fixed it in a separate branch as a PR #162. Here. Not sure why that wasn't caught?

[nucleogenesis]

Ah I missed that - good eye @indirectlylit !