hydev777

import 'package:flutter/material.dart';

import '../view/bottom_proposal_menu.dart';

class ProposalBottomNav extends StatefulWidget {
  const ProposalBottomNav({super.key});

  @override
  State<ProposalBottomNav> createState() => _ProposalBottomNavState();
}

hydev777

class CustomHashSet {
  CustomHashSet();

  final _keys = List<List<int>>.generate(1000, (index) => []);
  
  List<List<int>> get keys {
    return _keys;
  }
  
  int _hashFunction(int key) {

hydev777

class Message {
  Message({ this.content, this.type });

  final String? content;
  final String? type;

}

class TextMessage extends Message {

hydev777

Commit Message Guidelines

We have very precise rules over how our git commit messages can be formatted. This leads to more readable messages that are easy to follow when looking through the project history. But also, we use the git commit messages to generate the Angular change log.

Commit Message Format

Each commit message consists of a header, a body and a footer. The header has a special format that includes a type, a scope and a subject: