We could use lernajs to ease multi packages management.

@bpaugam

mod-link on a button gives it a regular hyperlink look.

Problem is, I find that the spacing between text and underline is way too tight by default. I'd rather give it some extra space.

This could be achieved this way (that also prevents us from having to make the button relatively positioned):

https://codepen.io/benoitpaugam/pen/xPPzOr

This example also shows that sometimes, I would like a decorative element (the "+" sign here) not to be underlined. Which would be perfectly doable.

have an input that can be plugged to a moment.duration

add possible overlay/picker so we can add 5/15 mins at a time without having to type it

must support inputing in number of days or hours

might have some problems with the @lucca-front/scss: 0.0.0-VERSIONPLACEHOLDER

add a loader in case the api querying gets lost in the internet's tubes

needs timer to avoid flashing if api pulses

https://blog.thoughtram.io/angular/2016/06/08/component-relative-paths-in-angular-2.html

tl;dr

// works
@Component({
  templateUrl: './my-stuff.component.html',
}) class MyStuff {}

// is bettor
@Component({
  templateUrl: 'my-stuff.component.html',
  moduleId: module.id,
}) class MyStuff {}

try to be up to date, i think i forgot to update it when releasing 0.1

add placehiolder when no result is available with current clue

add @input filter so we can add a filter to the queris to the api

ex: we want to plug an api-picker to /api/v3/currencies?isEnabled=true

@bpaugam

about qall the things you need to do to contribute to lucca-front

the diffrents steps to have your component created and added to the demo

We need 2 things in LF:

• [ng] An importable module that works in angular 4
• [scss] a set of precise easing function

feature of componenet described in #11

add @Input to specify which field are fetched from the api so they can be used in custom templates (see #181) or for the vontrol value

ex : i'm pinging /api/v3/currencies, i may wanna get the currency symbol

here

just call npm test and wire npm test to call lerna run test so it runs test for all packages of the lib

specs - in french with limited access

• the type autocomplete is unusable
• sometimes the select doesnt initiate well and doesnt display the current vaslue

feature of componenet described in #11

add possibility to specify a custom template for displaying each options

@bpaugam

maybe we have enough with @sanlucca animations + ngIf

Single module for single component => cf LuUserModule

rizzoma :'(

feature of componenet described in #11

support down/up keys and enter/esc to select an item in the dropdown

angular uses classes like ng-valid, ng-invalid, ng-pristine etc... it would be super usefull if the scss framework offered an option to have style automatically added to said classes

https://github.com/LuccaSA/lucca-front/blob/master/packages/ng/libraries/core/src/style/components/_input.scss

ng-material - ng-bootstrap

the idea is that we're gonna need modals, popovers, tooltips, selects and other usefull components and in the first version we're just gonna let a third party lib do it for us

points to check

• available features of each lib
• style overridability

Change the list of KeyCodes list as constants to an enum of string : cf remarq of @vergerf on PR #225

For the moment we have LuUserPictureComponent that resizes images with a width of 100px . But sometimes we need to display bigger images, so we can let the choice to developper to set the size: <lu-user-tile [user]="user" [picture-size]="200">

see with @sanlucca hoe to implement this with his animation factory

https://github.com/LuccaSA/Timmi.Timesheet/blob/inte/front/report/src/components/lf/_collapse.scss

could you provide a ReX on lerna and some best practice for using it once you've been using it for 2-3 months.

@bpaugam issue #11

@jeremie-lucca for you

assess the need for it and rework its inclusion in the lib

Verify that the Api Picker could be tolerant to non accent sensitive searchs :

cf LuccaSA/RestDrivenDomain#70

dont forget to mention the date implementation policy from ng mat

feature of componenet described in #11

supoport a form of paging for the api-picker component

you can query api with /api/v3/things?name=like,...&fields=id,name,collection.count&paging=0,10 and it will give you the number of items that satify name=like,... and only the detail of the first 10

:sad_face:

so we will have to hae a luInput directive that adds said c,asses when ngModel is empty

Il manque une documentation pour savoir quel import effectuer :/

import { LuSelectModule } from '@lucca-front';
ne fonctionne pas.

Je pense qu'il manque l'ajout de l'import du Select dans: le index.d.ts de ng.

export * from './app/date-range-picker/date-range-picker.module';
export { IDateRangeSelectChoice, IDateRange } from './app/date-range-picker/date-range-picker.model';
export * from './app/user';
export * from './app/popover';
export { LuRootModule } from './app/lu-root.module';
export { LuEmptyModule } from './app/empty';
export * from './app/animations';
export { LuFormlyModule } from './app/formly';
export * from './app/api';

(obliger de faire import { LuSelectModule } from '@lucca-front/ng/src/app/select';)
Uncaught Error: Can't resolve all parameters for LuPopoverComponent

L'impémentation de reactiveForm pose des problèmes.

<div class="textfield mod-block" [formGroup]="innerFormGroup">
  <lu-select
    formControlName="value"
    placeholder="placeholder">
      <lu-select-option *ngFor="let option of format.entries" [luOptionValue]="option">{{option.description}}</lu-select-option>
      <lu-select-clearer></lu-select-clearer>
  </lu-select>
</div>

Donne ERROR Error: No value accessor for form control with name: 'value'. (le formGroup a bien un contrôle 'value').

different from arrow_east cuz @bpaugam wants -> and not just >

add formly overlay for api-picker

use prescript to patch package.json or else npm i doesnt work because of the 0.0.0-placeholder used in /ng package

i totes commented the current daterange picker for release 0.1, we need to repare it for release 1.0.0

~300 lines of code and no tests, shame...